Enforce password strength constraint #209
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@Pr0Ger , is this PR still active ? If it actual, please update it and fix tests, otherwise close it. |
Pr0Ger
force-pushed
the
user_password_validation
branch
from
862035c
to
b0d39e2
Compare
Pr0Ger
force-pushed
the
user_password_validation
branch
from
b0d39e2
to
6f07af6
Compare
Pr0Ger
force-pushed
the
user_password_validation
branch
from
6f07af6
to
99863f3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have server-side check for password strength, this PR will add client side validation with same restrictions